Release 10.1A: OpenEdge Application Server:
Administration

Connecting to an OpenEdge RDBMS

WebSpeed supplies a demonstration OpenEdge database called Sports2000. You can use the Sports2000 database to run the sample applications and experiment with your first WebSpeed applications.

In a local configuration, the OpenEdge database resides on the same machine as the WebSpeed Transaction Server. The structure of a remote configuration can vary. OpenEdge Getting Started: WebSpeed Essentials shows some of the configuration possibilities. When you are developing in a client/server environment, you can connect to the database in single-user mode. When you develop WebSpeed applications on a Windows system with the WebSpeed Workshop, you must run the OpenEdge database in a multi-user mode. In the WebSpeed Workshop development environment, several agents must connect to the database simultaneously: one for the Progress Explorer, another for the WebSpeed WebTools, and one for the AppBuilder.

See the chapter on startup in the OpenEdge Data Management: Database Administration for more information on running the OpenEdge database server and the parameters that you can specify.

You provide the information that an agent needs to connect to a database when you configure a WebSpeed Transaction Server and specify the agent options for its pool of agents. The WebSpeed agent is a 4GL client running in batch mode and can accept nearly all the startup parameters a standard client can.

This is a sample srvrStartupParam setting in ubroker.properties for the sample Transaction Server, wsbroker1, running on a Windows system:

srvrStartupParam=-p web\objects\web-disp.p -cpstream iso8859-1 -weblogerror

WebSpeed provides many parameters that allow you to control connections to the database and make adjustments to increase performance. These include parameters for controlling record-buffer size, cursor size, and read-only access. In addition to database connection parameters, WebSpeed provides session parameters that allow you to control the conditions under which it compiles your r-code and Web objects and how to handle code page issues. See the OpenEdge Deployment: Startup Command and Parameter Reference for details on session parameters.